Fix documentation environment compatibility - #139
Merged
ChrisRackauckas merged 1 commit intoJul 30, 2026
Merged
Conversation
Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please ignore this PR until reviewed by @ChrisRackauckas.
Summary
Restore the documentation environment's RuntimeGeneratedFunctions compatibility from
0.6to0.5, matching the package's current v0.5.23 version.Root cause
#136 moved both the package version and docs compatibility to 0.6. #137 then changed the package back to 0.5.23 but left
docs/Project.tomlrequiring 0.6. As a result, the reusable Documentation workflow fails duringPkg.develop(PackageSpec(path=pwd())), before it can build any docs:An actual Pkg-based git bisect from v0.5.22 (
18e4b5d) through current master identified #137 (483e2e938e1bfc5b5df6dc3aab0064c7005d08b6) as the first bad commit; #136 (6550973d9290c906b1f61d37d416695e95e63a7c) is the passing control with both versions at 0.6.This independent clean-master failure was exposed while auditing #138. It is not caused by that serialization change.
Validation
Using Julia 1.12.6, matching CI:
julia --project=docs/ -e 'using Pkg; Pkg.develop(PackageSpec(path=pwd())); Pkg.instantiate()'julia --project=docs/ docs/make.jl(doctests, link checks, document checks, and HTML rendering)julia --project=. -e 'using Pkg; Pkg.test()'--check --diff .Clean-master failure evidence: